Fix "lisp nesting exceeds max-lisp-eval-depth" errors on MS-Windows.

This happens during bootstrap; see bug#11649.

 lisp/makefile.w32-in (BIG_STACK_DEPTH): Enlarge to 2200.

diff --git a/lisp/ChangeLog b/lisp/ChangeLog
index 7dbce3ec657479cb19409c9142cd3df1cb3a3106..197e1f98f76c5c3f7b91e537c5fcbeac1637ce88 100644 (file)
--- a/lisp/ChangeLog
+++ b/lisp/ChangeLog
@@ -1,3 +1,7 @@
+2012-06-09  Eli Zaretskii  <eliz@gnu.org>
+
+       * makefile.w32-in (BIG_STACK_DEPTH): Enlarge to 2200.  (Bug#11649)
+
 2012-06-09  Chong Yidong  <cyd@gnu.org>
 
        * face-remap.el (face-remap-add-relative, face-remap-set-base)

diff --git a/lisp/makefile.w32-in b/lisp/makefile.w32-in
index 6cb8b3dd4955fbf31a09d952953c0b04ac2cc83a..cdfdf383de89cdfbb8112d6a6de384eb7860a252 100644 (file)
--- a/lisp/makefile.w32-in
+++ b/lisp/makefile.w32-in
@@ -70,7 +70,7 @@ AUTOGENEL = $(lisp)/loaddefs.el $(LOADDEFS) $(lisp)/cus-load.el \
 # During bootstrapping the byte-compiler is run interpreted when compiling
 # itself, and uses more stack than usual.
 #
-BIG_STACK_DEPTH = 1200
+BIG_STACK_DEPTH = 2200
 BIG_STACK_OPTS = --eval "(setq max-lisp-eval-depth $(BIG_STACK_DEPTH))"
 
 BYTE_COMPILE_FLAGS = $(BIG_STACK_OPTS) $(BYTE_COMPILE_EXTRA_FLAGS)